[pnpm](https://github.com/pnpm/pnpm) is a package manager optimized for monorepos.
It is faster than NPM and consumes less disk storage than Yarn.

Disk consumption:
- Yarn
```sh
$ du -sh ~/workspace/acre/acre
2.2G    /Users/jakub/workspace/acre/acre
```
- pnpM
```sh
$  du -sh ~/workspace/acre/acre
875M    /Users/jakub/workspace/acre/acre
```

To install pnpm with Homebrew run `brew install pnpm`, for other installation options
please see the [documentation](https://pnpm.io/installation).

To install the packages dependencies run:
```sh
pnpm install
```

Use pnpm instead of yarn in CI workflow.

Define `packageManager` in `package.json` so the `pnpm/action-setup@v2`
job uses it to setup the correct pnpm version.

Gatsby requires a plugin to work with pnpm.

Be explicit in the command that we want to run a script and pass the
paratemeters to the script

Instead of adding dependencies we define public-hoist-pattern property
for @chakra-ui/* packages.

Read more on public-hoist-pattern here: https://pnpm.io/npmrc#public-hoist-pattern

The fix was suggested in chakra-ui/chakra-ui#6427 (comment)

Define main .gitignore in the root directory with a common rules and
separate .gitignore files with module-specific rules.

dApp and website docs were missing pnpm commands.

The root directory contains package.json, so it is worth adding the
.nvmrc file for consistency.

When npmrc was defined with public hoist in the `dapp` directory it
required installation of the dependencies to happen inside the `dapp`
directory to correctly resolve the `@chakra-ui/theme-tools` dependency.

With moving the file to the root directory, installation of the
dependencies inside the root directory will correctly resolve
`@chakra-ui` dependencies inside the `dapp` sub-project.

The job has to be updated to use pnpm instead of yarn.